Expected Regressions

  • Scenario level extractions were removed as a functionality and zeroed out. This will create deltas when reporting at the scenario level in projects where this opaquely defined input existed. See How to Migrate Scenario Level Extractions for more information.
  • Asset level defined user data’s phase out may cause deltas where the functionality is chosen to be deleted and it previously had a calculation effect, or where it has been converted to project level data but where edge cases may have existed in subsequent function references (phasing out)
  • Consolidation Links have undergone significant revision to resolve bugs. Any project using this is likely to see regressions
  • Land All Grid has had two extra columns added for the reversion triggering effective dates. This may cause workflow issues where a fixed format of the paste was defined on the previous shape
  • Well list specified flows to will now result in a reroute task being executed when there is a -1 well count (previously ignored)
  • Reporting from PDS will see the additional value of Rate of Take now populated correctly (rather than 0) as well as the save date and time if using %DATETIME% report tag
  • Recently converted static wells were having their mob / demob times doubled, which has now been fixed. This may have created slight schedule differences along with subsequent downstream effects (Production, Revenue, Opcost...)
  • Differences in the production results (and subsequent economic considerations) are expected when:
    • Swapping to the new 3.0 solver. This may also manifest itself as an identical scenario level result for production with different economic results due to traversing other paths and triggering their alternative economics inputs being applied. Any project changing solvers will likely see some regressions. See How to Swap Solver Types for more information.
    • Using function inputs on constraints and running daily, where well decline segments transition due to bug fixes removing overlap of segments, previously causing spikes in production
    • Using functions @DeclineSetIndex() and @DeclineTime() due to bug fixes
    • Volumetric downtime specified at facilities as applying against wells which have history data as this is now ignored similarly to fractional downtime
  • Royalties:
    • US Severance and Ad Valorem may be higher due to removing the effect of deductible costs being applied against $/bbl and $/mcf type taxes (they should only apply against fixed or percentage-based taxes)
    • BC Royalties may be lower where NGL related Opex was inputted using a function as it previously wasn’t being deducted correctly
    • Alberta Royalties may be higher where the Effective Royalty Rate for the MRF is now correctly incorporating fuel and flare volumes into its evaluation